-
Notifications
You must be signed in to change notification settings - Fork 3.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hop nodes for k8s #13904
Hop nodes for k8s #13904
Conversation
d2662b9
to
056326e
Compare
687df1f
to
91efa83
Compare
89be8dc
to
c32a37b
Compare
2e1146e
to
c451a63
Compare
b37ac4e
to
72a1cb4
Compare
72a1cb4
to
05b2b5d
Compare
05b2b5d
to
f6f7ba5
Compare
24f2122
to
f75b9ba
Compare
in operator check:
This is fixed with ansible/ansible-runner#1268 |
dbeacf9
to
c51e8f0
Compare
6b37dd6
to
00c6975
Compare
This reverts commit cf5ccf5.
Dynamically flipping from Established to Disconnected is not the intended usage of InstanceLink State. - Link state starts in Adding and becomes Established once any control node first sees the link is in the status KnownConnectionCosts
API changes - cannot change peers or enable peers_from_control_nodes on VM deployments - allow setting ip_address - use ip_address over hostname in the generated group_vars/all.yml - Drop api/v2/peers endpoint DB changes - add ip_address unique constraint, but ignore "" entries Other changes - provision_instance should take listener_port option Tests - test that new controls doesn't disturb other peers relationships - test ip_address over hostname
Get rid of PeersSerializer and just use SlugRelatedField, which should be more a straightforward approach. Other changes: - cleanup code related to the already-removed api/v2/peers endpoint - add "hybrid" node type into more instance_peers test cases
Add a check_peers_changed() utility method to determine if peers in attrs matches the current instance peers. Other changes: - Set ip_address default to "", and do not allow null.
Setting a different value for ip_address and hostname does not work with the current way we create receptor certs.
Make test case cleaner by using itertools product instead of the triple nested loop Replace triple single quotes with triple double quotes
Might help to install receptor last, that way when nodes are first connected to the mesh they already have podman installed and can potentially run jobs. Otherwise it might be possible for controller to launch jobs against nodes that aren't fully set up.
receptor_host_identifier can be left out of group_vars and will default to the 'ansible_host' variable
0746984
to
8a4678c
Compare
@@ -7,14 +7,11 @@ | |||
user: | |||
name: "{{ receptor_user }}" | |||
shell: /bin/bash | |||
- name: Enable Copr repo for Receptor | |||
command: dnf copr enable ansible-awx/receptor -y |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't this be removed from previous installed receptors?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
sorry, can you clarify the question? The next receptor-collection version will install receptor via these releases by default https://github.com/ansible/receptor/releases
thus the Copr repo is no longer needed going forward
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm thinking of upgrades of previous installs.
version: 1.1.0 | ||
- name: https://github.com/ansible/receptor-collection.git | ||
type: git | ||
version: main |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
do we need to point this to 2.0.0 version?
@@ -40,7 +40,7 @@ echo "Admin password: ${DJANGO_SUPERUSER_PASSWORD}" | |||
awx-manage create_preload_data | |||
awx-manage register_default_execution_environments | |||
|
|||
awx-manage provision_instance --hostname="$(hostname)" --node_type="$MAIN_NODE_TYPE" | |||
awx-manage provision_instance --hostname="$(hostname)" --node_type="$MAIN_NODE_TYPE" --listener_port=2222 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This concerns me a little bit about the expected practice. Does this need to be provided for VM installs in general? I don't get why we didn't need this before, but would now.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So it seems that this is not required, and as such, it would make the most sense to not set it here, because the VM install scenario that this corresponds to should not ordinarily be setting the listener port.
Filed a followup issue #14387 |
SUMMARY
Allow users to setup hop nodes for k8s deployments
ISSUE TYPE
COMPONENT NAME
AWX VERSION